Vehicle alert system using mobile location information

ABSTRACT

A method includes receiving location data related to devices transmitted during a first interval. The location data includes at least two GPS points of a first device and a single GPS point of a second device. The method includes identifying a subset of the devices that are within a vicinity of an area associated with a traffic event based on the data. The method includes determining that the first device will not approach the area during a second interval based on the two GPS points and determining that the second device will not approach the geographic area during the second interval based at least on the single GPS data point and a second location datum. The method includes filtering the first and second devices from the subset and transmitting an alert indicative of the traffic event to the subset.

TECHNICAL FIELD

The technical field generally relates to vehicle alerts and, morespecifically, to identifying recipients to alert of a traffic event.

BACKGROUND

Road conditions may change dynamically due to a wide variety of causeswhere no prior avoidance notification is available to drivers. A commonresult of a driver's sudden realization of a hazardous condition is tobrake hard or to swerve to avoid the hazard. This may be true for bothtransient traffic conditions, such as those caused by a trafficaccident, and for chronic road conditions, such as at a blind turn wheredrivers regularly slow down. Alerting drivers of impending roadconditions may be advantageous.

SUMMARY

Disclosed herein are systems, methods, and apparatuses that assist inproviding alerts to vehicles that may encounter a traffic event. Thedisclosed systems, methods, and apparatuses may include differentsolutions pertaining to identifying recipients, from a plurality ofdevices, of these alerts.

In an aspect, this disclosure is directed to a method. The method mayinclude receiving, at a network device of a network, location datatransmitted during a first time interval. The location data may berelated to a plurality of devices. The location data may include atleast two global positioning system (GPS) data points of a first device,a single GPS data point of a second device, and information related to avelocity of a third device. The method may include identifying, based atleast on the location data, a subset of the plurality of devices thatare within a vicinity of a geographic area associated with a trafficevent. The subset may comprise the first device, the second device, thethird device, and a fourth device. The method may include filtering, bythe network device, the third device from the subset based at least onthe information related to the velocity of the third device indicatingthat the velocity of the third device does not exceed a threshold. Themethod may include determining that the first device will not approachthe geographic area during a second time interval based at least on theat least two GPS data points. The method may include determining thatthe second device will not approach the geographic area during thesecond time interval based at least on the single GPS data point and asecond location datum. The method may include filtering, by the networkdevice, the first device and the second device from the subset andtransmitting, via the network, an alert indicative of the traffic eventto the subset.

In another aspect, this disclosure is directed to a system. The systemmay include an input/output and a processor communicatively coupled tothe input/output. The system may include memory storing instructionsthat cause the processor to effectuate operations. The operations mayinclude receiving, via the input/output, location data transmittedduring a first time interval. The location data may be related to aplurality of devices. The location data may include at least two globalpositioning system (GPS) data points of a first device, a single GPSdata point of a second device, and information related to a velocity ofa third device. The operations may include identifying, based at leaston the location data, a subset of the plurality of devices that arewithin a vicinity of a geographic area associated with a traffic event.The subset may include the first device, the second device, the thirddevice, and a fourth device. The operations may include filtering thethird device from the subset based at least on the information relatedto the velocity of the third device indicating that the velocity of thethird device does not exceed a threshold. The operations may includedetermining that the first device will not approach the geographic areaduring a second time interval based at least on the at least two GPSdata points and determining that the second device will not approach thegeographic area during the second time interval based at least on thesingle GPS data point and a second location datum. The operations mayinclude filtering the first device and the second device from the subsetand transmitting, via the input/output, an alert indicative of thetraffic event to the subset.

According to another aspect, this disclosure is directed to a method.The method may include receiving, at a network device of a network,location data transmitted during a first time interval. The locationdata may be related to a plurality of devices and may include at leasttwo global positioning system (GPS) data points of a first device and asingle GPS data point of a second device. The method may includeidentifying, based at least on the location data, a subset of theplurality of devices by filtering out a distant device that is outsideof a vicinity of a geographic area associated with a traffic event. Thesubset may include the first device, the second device, and a thirddevice. The method may include determining that the first device willnot approach the geographic area during a second time interval based atleast on the at least two GPS data points. The method may includedetermining that the second device will not approach the geographic areaduring the second time interval based at least on the single GPS datapoint and a second location datum. The method may include filtering, bythe network device, the first device and the second device from thesubset and transmitting, via the network, an alert indicative of thetraffic event to the subset.

In an aspect, this disclosure is directed to a method. The method mayinclude identifying devices that are within a vicinity of a geographicarea affected by a traffic event based on location data of the devices.The method may include determining a subset of the devices that areestimated to approach the geographic area within the second timeinterval, the subset of devices comprising a first device and a seconddevice. The method may include estimating that the first device willapproach the geographic area within the first time interval based on atleast two timestamped global positioning system (GPS) data points fromwithin a second time interval. The method may include estimating thatthe second device will approach the geographic area within the secondtime interval based on exactly one GPS data point from within the secondtime interval and the second location data. The method may also includetransmitting, to the subset of the devices, an alert of the trafficevent.

In an aspect, this disclosure is directed to a method. The method mayinclude identifying devices that are within a vicinity of geographicarea affected by a traffic event based on location data of the devices.The method may also include, for a first device of the devices, whereinlocation data of the first device comprises at least two timestamped GPSdata points within a time interval, estimating whether the first devicewill approach the geographic area within a second time interval based atleast on the at least two timestamped GPS data points. The method mayalso include, for a second device of the devices, wherein the locationdata of the second device comprises a second location data and exactlyone timestamped GPS data point within the time interval, estimatingwhether the second device will approach the geographic area within thesecond time interval based on the exactly one GPS data point and thesecond location data. The method may also include determining a subsetof the devices that are estimated to approach the geographic area withinthe second time interval and transmitting, to the subset of the devices,an alert of the traffic event.

In another aspect, this disclosure is directed to a system. The systemmay include an input/output and a processor communicatively coupled tothe input/output. The system may also include memory storinginstructions that cause the processor to effectuate operations. Theoperations may include identifying devices that are within a vicinity ofgeographic area affected by a traffic event based on location data ofthe devices. The operations may also include, for a first device of thedevices, wherein location data of the first device comprises at leasttwo timestamped GPS data points within a time interval, estimatingwhether the first device will approach the geographic area within asecond time interval based at least on the at least two timestamped GPSdata points. The operations may also include, for a second device of thedevices, wherein the location data of the second device comprises asecond location data and exactly one timestamped GPS data point withinthe time interval, estimating whether the second device will approachthe geographic area within the second time interval based on the exactlyone GPS data point and the second location data. The operations may alsoinclude determining a subset of the devices that are estimated toapproach the geographic area within the second time interval andtransmitting, to the subset of the devices, an alert of the trafficevent.

In accordance with another aspect, this disclosure is directed to amethod. The method may include identifying a traffic event that isaffecting a geographic area and identifying a plurality of devices thatare within a vicinity of the geographic area based on location dataassociated with the plurality of devices. The location data maycomprising, for each of the plurality of devices, at least one globalpositioning system (GPS) data point and a corresponding time data point.The plurality of devices may comprise a first group of devices and asecond group of devices. Each device of the first group may beassociated with at least two GPS data points having corresponding timedata points with a time interval, and each device of the second groupmay be associated with exactly one GPS data points having correspondingtime data point within the time interval. The method may include, foreach device of the first group, based on the at least two GPS datapoints associated with the device, estimating whether the device willapproach the geographic area within a time threshold. The method mayinclude, for each device of the second group, based on a second locationdatum associated with the device and the exactly one GPS data point,estimating whether the device will approach the geographic area withinthe time threshold. The method may include compiling each device of thefirst group that is estimated to approach the geographic area within thetime threshold and each device of the second group that is estimated toapproach the geographic area within the time threshold to a subset ofthe plurality of devices. The method may include transmitting, to thesubset of devices, an alert indicative of the traffic event.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described vehicle alert systems and methods aredescribed more fully with reference to the accompanying drawings, whichprovide examples. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providean understanding of the variations in implementing the disclosedtechnology. However, the instant disclosure may take many differentforms and should not be construed as limited to the examples set forthherein. Where practical, like numbers may refer to like elementsthroughout the application.

FIG. 1 illustrates an exemplary system for communicating vehicle alerts.

FIG. 2 is a flowchart for an exemplary method of detecting a trafficevent affecting a geographic area.

FIG. 3 is a schematic of an exemplary network device.

FIG. 4A is a flowchart of an exemplary method for communicating alertmessages.

FIG. 4B is a flowchart of an exemplary method for communicating alertmessages.

FIG. 5 is a flowchart of an exemplary method for communicating alertmessages.

FIG. 6 is a flowchart of an exemplary method for communicating alertmessages.

FIG. 7 is an exemplary network architecture.

FIG. 8 depicts an exemplary communication system that provides wirelesstelecommunication services over wireless communication networks.

FIG. 9 illustrates an exemplary architecture of a GPRS network.

FIG. 10 is a block diagram of an exemplary public land mobile network(PLMN).

DETAILED DESCRIPTION

FIG. 1 illustrates a telecommunication system in which one or moredevices 102, such as wireless transmit/receive units (WTRUs) or othernetwork-connectable devices, may communicate via one or more accesspoints, such as base stations 104 or Wi-Fi access points 106, to one ormore networks. For example, devices 102 may include one or more end userdevices, such as personal computers, tablets, smart phones, or othermobile devices; physical devices, like lighting equipment, televisions,home appliances, or the like; sensors or sensor-equipped systems,including health monitors, biometric sensors, sensors that trackstatistics on objects, environments, or other things; vehicles 103including manned and unmanned vehicles, whether or not autonomous,robotic devices, machinery, and the like. Devices 102 may include othernetwork-connected devices, including servers and backend systems.Devices 102 may include Internet of things (IoT) devices and devicesthat may communicate with IoT devices. Devices 102 may include devicesthat communicate through networks or technology other than cellularnetworks, such as those having 802.11XX connectivity.

While FIG. 1 illustrates each device 102 as a single device, device 102may comprise related but distinct components. For example device 102 aillustrates an end user device 103 a, that is capable of receivingalerts via a network, such as a mobile phone, and a related device 103 bthat is related to end device 103 a. Related device 103 b may be anotherend device capable of receiving alerts via a network without device 103a relaying such alerts, such as another mobile device that has some typeof relationship with device 103 a. Alternatively, related device 103 bmay be linked to network via device 103 a, such as a Bluetooth® orNFC-connected device that communicates with device 103 a, such as awearable device, like a health monitoring device or a smart watch.Devices 103 a and devices 103 b may have some type of relationship toone another, such that together they may be treated as device 102, forpurposes of determining their location or communicating alerts based ontheir location. For example, device 103 b and device 103 a may be linkedto the same user account, or they may be linked to different users on afamily plan. Historical behavior may indicate that devices 103 a anddevices 103 b are used together, or are co-located, at least a certainpercentage of time, or during certain time periods of the day, week,month, or year, etc. As another example, devices 103 a and 103 b may bein communication with one another, such as via wireless (e.g. Bluetooth®or NFC technologies) or wired communication.

Each of base stations 104 may be any type of device configured towirelessly interface with at least one device 102 to facilitate accessto or communication with network 118. By way of example, base stations104 may be a base transceiver station (BTS), a Node-B, an eNode B, aHome Node B, a Home eNode B, a site controller, an access point (AP), awireless router, or the like. While base stations 104 are each depictedas a single element, it will be appreciated that base stations 104 mayinclude any number of interconnected base stations or network elements.

Each of wireless access points 106 may be any type of device configuredto wirelessly interface with at least one device 102, such as vehicles103, to facilitate access or communication with one or more networksthrough an internet service protocol. For example, wireless access point106 using a wireless protocol such as Bluetooth, Zigby, WiGig, or one ormore of the variants of the IEEE 802.11 protocol. For example, wirelessaccess point 106 may include a Wi-Fi hotspot, a router, or the like.

Telecommunication system 100 may include one or more networks, such as aradio access network (RAN) 108, a core network 110, a wireless localarea network (WLAN) 111, the Internet 112, or other networks 114. Thedisclosed examples contemplate any number of devices 102, base stations104, wireless access points 106, networks, or network elements.

RAN 108 may include one or more base stations 104, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 104 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 104 may be divided intothree sectors such that base station 104 may include three transceivers:one for each sector of the cell. In another example, base station 104may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 104 may communicate with one or more of devices 102 overan air interface, which may be any suitable wireless communication link(e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV),or visible light). The air interface may be established using anysuitable radio access technology (RAT).

More specifically, as noted above, telecommunication system 100 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 104 in RAN 108 and devices 102, such as vehicles103, connected to RAN 108 may implement a radio technology such asUniversal Mobile Telecommunications System (UMTS) Terrestrial RadioAccess (UTRA) that may establish air interface using wideband CDMA(WCDMA). WCDMA may include communication protocols, such as High-SpeedPacket Access (HSPA) or Evolved HSPA (HSPA+). HSPA may includeHigh-Speed Downlink Packet Access (HSDPA) or High-Speed Uplink PacketAccess (HSUPA).

As another example, base station 104 and devices 102, such as vehicles103, that are connected to RAN 108 may implement a radio technology suchas Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establishcommunication using LTE or LTE-Advanced (LTE-A).

Optionally base station 104 and devices 102, such as vehicles 103,connected to RAN 108 may implement radio technologies such as IEEE602.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)),CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000),Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), GSM,Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or thelike.

Base station 104 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 104 and associated devices 102 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 104 and associated devices 102 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 104and associated devices 102 may utilize a cellular-based RAT (e.g.,WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell orfemtocell.

RAN 108 may be in communication with core network 110, which may be anytype of network configured to provide voice, data, applications, orvoice over internet protocol (VoIP) services to one or more devices 102,such as vehicles 103. For example, core network 110 may provide callcontrol, billing services, mobile location-based services, pre-paidcalling, Internet connectivity, video distribution or high-levelsecurity functions, such as user authentication. Although not shown inFIG. 1, it will be appreciated that RAN 108 or core network 110 may bein direct or indirect communication with other RANs that employ the sameRAT as RAN 108 or a different RAT. For example, in addition to beingconnected to RAN 108, which may be utilizing an E-UTRA radio technology,core network 110 may also be in communication with another RAN (notshown) employing a GSM radio technology.

Core network 110 may also serve as a gateway for devices 102, such asvehicles 103, to access Internet 112 or other networks 114. Internet 112may include a global system of interconnected computer networks ordevices that use common communication protocols, such as TCP, userdatagram protocol (UDP), or IP in the TCP/IP internet protocol suite.Other networks 114 may include wired or wireless communications networksowned or operated by service providers that differ from the serviceprovider that owns or operates core network 110. For example, othernetworks 114 may include another core network connected to one or moreRANs, which may employ the same RAT as RAN 108 or a different RAT.

Some or all devices 102 in telecommunication system 100 may includemulti-mode capabilities. That is, devices 102 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more devices 102 may beconfigured to communicate with base station 104, which may employ acellular-based radio technology, and with access point 106, which mayemploy an IEEE 802 radio technology.

Telecommunication system 100 may include functionality for communicatingvehicle alerts. For example, telecommunication system 100 may include analert server 116. Alert server 116 may comprise any appropriate type ofequipment, such as, for example, a computer, a server, a mobile device,a tablet, or any type of equipment capable of receiving and processingacceleration and location data to facilitate identifying traffic events,devices 102 that may be imminently impacted by that traffic event, andrelaying alerts of the traffic event to those identified devices. Alertserver 116 may receive an alert from an originator. Additionally oralternatively, alert server 116 may determine that a traffic event hasoccurred and in response generate the alert. In an aspect, alert server116 may comprise or be in communication with core network 110. Forexample, alert server 116 may be controlled by the service provider ornetwork operator of core network 110.

Alert server 116 may communicate alerts to vehicles 103. A traffic eventmay be characterized by a sudden change in speed or acceleration oftraffic. A traffic event may affect a geographic area. A geographic areamay include, for example, a traffic lane, a stretch of a highway, astreet, an on-ramp, an off-ramp, an intersection, the like, or anycombination thereof. The precision of how the geographic area may vary.For example, a geographic area may include roads on which traffic istraveling in a particular direction (e.g., away from a city center),certain traffic lanes on a highway (e.g., non-HOV lanes on I-75S), orany other defined scope. Detecting a traffic event may be based onsensor data collected from one or more devices 102 proximate to thegeographic area.

FIG. 2 is a flowchart for an exemplary method 200 that may be usedwithin system 100 for detecting a traffic event. At step 202, method 200may include receiving sensor information from a plurality of devices102. The sensor information may comprise location information, such asGPS locations or cell ids, speed information, such as lateral or linearspeed, acceleration information, such as lateral or linear information,or the like. Step 202 may include filtering sensor information. Forexample, sensor information originating from devices 102 that arestationary or outside of a proximity of the geographic area may befiltered out. Further, sampling of the sensor information may be done.

At step 204, a traffic flow of the geographic area may be derived basedon a subset of the sensor information. For example, the traffic flow maybe an acceleration pattern of the geographic area. As another example,the traffic flow may be a velocity pattern of the geographic area. Thetraffic flow may be multi-faceted. For example, the acceleration patternor velocity pattern may be measured in line with the shape of thegeographic area (e.g., measuring acceleration or speed along the road orother geographic area). Optionally, the acceleration or velocity patternmay also be measured laterally to the shape of the geographic area. Forexample, this lateral measurement may be used to identify where vehicles103 are swerving, such as to avoid an object in the road or as a resultof road conditions (e.g., potholes, ice).

At step 206, method 200 may include comparing the traffic flow toanother traffic flow. For example, another traffic flow may include aspeed limit, historical traffic flows, traffic flows for othergeographic areas near the geographic area. For example, comparing thetraffic flow to historical traffic flows can be used to detect anomalousevents, such as a car accident, that is affecting the current trafficflow. As another example, comparing the traffic flow to historicaltraffic flows could be sued to detect time-based events, such asrush-hour induced slowdowns. As yet another example, comparing thetraffic flow to a traffic flow for a nearby geographic area could beused to detect sudden changes in speed or acceleration. For example,comparing the acceleration pattern of an upstream or downstreamgeographic area can indicate that a bottleneck exists at the geographicarea. Thus, based on the comparing of step 206, at step 208, method 200may include determining whether a traffic event is affecting thegeographic area.

The comparing may also provide additional data regarding the trafficevent. For example, at step 210, method 200 may include identifying oneor more characteristics of the traffic event. For example, as discussedabove, the comparing may indicate that the traffic event is time-relatedevent, such as rush hour. Regularly occurring traffic events, such asrush-hour induced traffic congestion, may be identified as chronic.Other chronic traffic events may include those that are present for athreshold period of time. For example, a chronic traffic event mayinclude a bottleneck in which traffic regularly slows suddenly, such asa blind curve or a narrowing of the lanes. As another example, a chronictraffic event may include a pothole or object in the road that has beenpresent for a predefined period of time. The period of time by which atraffic event is considered chronic may vary. For example, the period oftime may depend upon such factors as the type of traffic event (e.g.,pothole or blind curve), how much the event impacts the traffic flow, orthe like. Other characteristics of the traffic event may include thelength of the geographic area, the impact the traffic event has on thetraffic flow (e.g., how long of a delay the traffic event creates), thetype of traffic event, or the like.

Method 200 may also include identifying traffic events or the geographicareas they affect based on additional or different data. For example,traffic events may also be identified based on user-input data, reportsof traffic events, such as those from users of devices 102,communications with emergency response systems, such as public-safetyanswering points, radio communications of fire or police departments,news reports, or other data sources. These secondary data sources may beused alone or in conjunction with sensor data from devices 102 toidentify traffic events.

FIG. 3 is a block diagram of a network device 300. Network device 300may be used for detecting traffic events or communicating or displayingalerts of traffic events. Network device 300 may be connected to orcomprise a component of telecommunication system 100. For example, oneor more of devices 102, related devices 103 a and 103 b, access points106, or alert server 116 may comprise all or a portion of network device300. Network device 300 may comprise hardware or a combination ofhardware and software.

The functionality to facilitate telecommunications via atelecommunications network may reside in one or a combination of networkdevices 300. Network device 300 depicted in FIG. 3 may represent orperform functionality of an appropriate network device 300, orcombination of network devices 300, such as, for example, a component orvarious components of a cellular broadcast system wireless network, aprocessor, a server, a gateway, a node, a mobile switching center (MSC),a short message service center (SMSC), an ALFS, a gateway mobilelocation center (GMLC), a radio access network (RAN), a serving mobilelocation center (SMLC), or the like, or any appropriate combinationthereof. It is emphasized that the block diagram depicted in FIG. 3 isexemplary and not intended to imply a limitation to a specificimplementation or configuration. Thus, network device 300 may beimplemented in a single device or multiple devices (e.g., single serveror multiple servers, single gateway or multiple gateways, singlecontroller or multiple controllers). Multiple network entities may bedistributed or centrally located. Multiple network entities maycommunicate wirelessly, via hard wire, or any appropriate combinationthereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength. As evidentfrom the description herein, network device 300 is not to be construedas software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 3) to allow communications therebetween. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork device 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example input/output system 306may include a wireless communications (e.g., 3G/4G/GPS) card.Input/output system 306 may be capable of receiving or sending videoinformation, audio information, control information, image information,data, or any combination thereof. Input/output system 306 may be capableof transferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 may also contain one ormore network connections 308 that allows network device 300 tofacilitate communications between devices 102 and networks, such as WLAN111 or Internet 112. Network connections 308 may comprise communicationmedia. Communication media typically embody computer-readableinstructions, data structures, program modules or other data in amodulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. By way ofexample, and not limitation, communication media may include wired mediasuch as a wired network or direct-wired connection, or wireless mediasuch as acoustic, RF, infrared, or other wireless media. The termcomputer-readable media as used herein includes both storage media andcommunication media. Input/output system 306 also may include an inputdevice 310 for receiving user inputs, such as keyboard, mouse, pen,voice input device, or touch input device. Input/output system 306 mayalso include an output device 312, such as a display, speakers,vibration outputs, or a printer.

For example, device 102 or access point 106 may comprise network device300 in which input/output system 306 may include an IEEE802.11-compliant transceiver. Optionally, input/output system 306 ofdevice 102 or access point 106 may also include a transceiver forcommunicating with a cellular network, such as core network 110, throughone or more RANs 108. Further, input/output system 306 of access point106 may include one or more network connections for connecting otherdevices 102 to a network, such as Internet 112.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for generating or processingalerts, as described herein. For example, processor 302 may be capableof, in conjunction with any other portion of network device 300,providing sensor data or traffic flow patterns to determine trafficevents, identifying recipients of an alert of a traffic event,transmitting alerts of traffic events, or receiving alerts of trafficevents, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to generate, transmit, or receive alerts of traffic events.

On a traffic event or geographic area affected by a traffic event isdetected, devices 102 that may be impacted by the traffic event—such asdevices 102 approaching the geographic area within a certain timeperiod—may be identified. There are multiple ways of identifying suchdevices 102. For example, given a plurality of devices 102, anaffirmative approach may be used to identify which devices 102 arepredicted to approach the geographic area. As another example, for thesame plurality of devices 102, a process of elimination may be used, inwhich devices 102 that are not expected to approach the geographic areaare filtered from a subset of the plurality of devices 102 beforealerting the devices of that subset. As yet another example, the subsetto which the alert is communicated may be identified by a combination ofadding certain devices 102 and removing certain other devices 102. Forexample, for since devices 102 may be operating under differentconditions, it may not be possible to affirmatively confirm or deny thata particular device 102 will approach geographic area based on thelocation data available for that particular device 102. When dealingwith a large number of a plurality of devices, a method for selectingthe subset to alert may also include making certain assumptions toefficiently communicate the alert.

FIG. 4A is a flowchart of an exemplary method 400 for alerting devices102 of a traffic event. At step 402, method 400 may include identifyinga traffic event that is affecting a geographic area. As an example, step402 may be performed by all or a portion of method 200.

At step 404, method 400 may include identifying devices 102 that arewithin a vicinity of a geographic area based on location data associatedwith devices 102. The location data of a device may indicate itslocation at a point in time. For example, the location data may comprisea GPS data point. Location data may comprise data regarding the identityand location access points 106 detected by device 102 and the strengthof the signals that device 102 detected from such access points 106.Location data may comprise data regarding the identity of the basestation(s) 104 or access point(s) 106 with which device 102 isconnected, or which device 102 can detect. For example, location datamay include the cell id of the cell in which device 102 is located. Forexample, the cell id may correspond to the base station 104. As anotherexample, handovers (or handoffs) between base stations 104 or accesspoints 106 may also be location data.

The accuracy of the location data may depend upon the type of thelocation data. For example, GPS data points may have an accuracy on theorder of about 3.5 meters. As another example, device 102's detection ofaccess point 106 may indicate device 102's location with approximately400 meter accuracy. As another example, a cell id may identify ageographic location on the order of 1 to 30 kilometers. These accuraciesmay be affected based on specific factors in a given situation. Forexample, GPS data points may be less accurate in locations denselypopulated by high rises, as a result of multi-path interference. Asanother example, the accuracy of a location based on device 102detecting access point 106 may depend upon the operating characteristicsof access point 106. Further, the size of a cell (and in turn, theaccuracy of a location based on device 102 being in a cell) may varybased on density of base stations 104 in the area.

Location data may be compiled together to improve accuracy. For example,the accuracy of a location based on device 102 being able to sensemultiple access points 106 may be greater than if the location was basedonly on device 102 sensing a single access point 106. As anotherexample, further considering signal strengths along with those detectedaccess points 106 may further improve accuracy. Location data may alsoinclude analysis of raw location data. For example, location data mayinclude a Rayleigh fading rate, trilateration based on multiplelocations (and optionally signal strengths), or other known locationtechniques.

Identifying devices 102 within a vicinity of the geographic area may bebased on the accuracy of location data associated with that particulardevice 102. For example, if the location of device 102 is based on GPSdata points, the vicinity may be a first threshold. As another example,if the location of another device 102 is based on lower-accuracy data,such as cell id, then the vicinity may differ. For example, it may bedesirable to filter out those devices 102 that, based on their GPSlocation, are more than 1 km downstream of the geographic area (e.g.,such that their GPS location indicates that even if such device 102 istraveling in the direction of the geographic area, the device 102 hasalready passed the traffic event). On the other hand, it may not beappropriate to eliminate devices 102 whose only location data indicatesthat they are within the cell that includes that location 1 kmdownstream of the geographic area, particularly if the same cell alsoincludes the geographic area and another geographic area that iscontiguous to and upstream of the geographic area affected by thetraffic event. Step 406 includes predicting or estimating that a subsetof devices 102 will approach the geographic area within a time interval.

For example, FIG. 5 illustrates a method 500 for estimating whether adevice 102 will approach the geographic area within the time intervalbased on at least two GPS data points. Step 502 may include identifyingat least two GPS points of device 102, and these GPS data points mayeach include a location point and a corresponding timestamp the locationdata of device 102. Step 504 may include calculating a speed vector fora particular device 102. For example, given at least two GPS points thateach include a location point and a corresponding timestamp, a vectorcan be calculated and used to estimate a future location of device 102.Thus, step 506 may include comparing the speed vector of a particulardevice 102 to the geographic area, as well as to the roadways thatconnect a GPS location of the particular device 102 to the geographicarea. This may include calculating a predicted time of arrival of device102 to the geographic area. The predicted time of arrival may bedetermined based on speed or acceleration patterns of device 102, whichmay also be calculated based on the location data of the particulardevice 102.

FIG. 6 illustrates a method 600 for determining whether a second device102 will approach a geographic area based on location data where suchlocation data includes at most one GPS data point within a timeinterval. For example, location data may include one GPS data pointwithin a time interval and a second location data of second device 102.As another example, the location data of second device 102 may includeno GPS data points within the time interval.

Thus, at step 602, method 600 may include second location data of thesecond device 102. Optionally, step 602 may include identifying a GPSdata point within the time interval of second device 102. As discussedabove, second location data may include non-GPS information (that is,location data that does not include or is not derived from GPS data),such as cell identifier, a Wi-Fi location, access point 106 detected bysecond device 102, access point 106 handoff, or a Rayleigh fading point.Additionally or alternatively, second location data may include ahistorical traffic activity of second device 102.

At step 604, method 600 may include determining whether second device102 is moving. This may be based on sensor data of second device 102(e.g., data from an accelerometer. Additionally or alternatively, thismay be based on other second location data, such as by comparing alocation indicated by the GPS data point to a location indicated byother second location data. At this stage, devices 102 that were notmoving, or are found to be moving away from the geographic area, may beeliminated and excluded from devices 102 that re alerted of the trafficevent.

Step 606 includes identifying those second devices 102 are estimated tobe moving towards the geographic area are identified. This estimationmay be based on the location history of second device 102 approachingthe geographic area. The estimation may further be based on the accuracyof second location data. Similarly, the time interval in which theestimated arrival of the geographic area is to occur) may also be basedon the second location data.

Returning to FIG. 4A, as mentioned above, step 406 may includedetermining whether the particular device will reach the geographic areawithin a time interval. This may be based on, for example, the predictedtime of arrival. The value of the time interval (e.g., within the next90 seconds, 5 minutes, etc.), may depend upon a variety of factors. Forexample, the time interval may be set based on the speed of device 102or a characteristic of the traffic event. For example, for devices 102traveling at slower speeds, the time interval may be smaller, as it maytake less time for the driver or device 102 to react to the trafficevent. By contrast, for devices 102 traveling at higher speeds, it maytake more time for driver or device 102 to react to the traffic event.As another example, for traffic events that cause a complete standstillof traffic, or which may be particularly dangerous, such as icyconditions, the time interval may be longer.

For devices 102 for which the location data is below an accuracythreshold, estimating whether those devices 102 will approach thegeographic area may involve different factors. For example, thosedevices 102 may not have location data that includes two GPS pointsusable for calculating a speed vector. For example, device 102 may nothave any GPS points associated with it. Alternatively, device 102 mayonly have expired GPS data points. That is, for predicting locationpatterns, the GPS points outside of a given time interval may beinaccurate. Setting this time interval may be based on a variety offactors, and it may be based on the particulars of a given device 102.For example, location data for a given device 102 that includes two GPSpoints, but those GPS points predate (by time) other types of locationdata (e.g., cell id, handover points, or sensed access points), and thatother location data is inconsistent with the GPS points, then it may beassumed that device 102 is no longer on the same trajectory suggested bythose two GPS points.

Optionally, identifying devices 102 to alert of the traffic event may bebased on other factors. For example, such other factors may include thedensity of the geographic area, the accuracy of device 102's locationdata, or the like. If the geographic area is in a high-density area,which may be based on the density of roadways, the amount of vehiculartraffic in the area, a highly populated area, or the like, then thethreshold for whether to alert a device may require the accuracy to meeta specific threshold. As another example, the estimated location ofdevice 102 may need to be within a specific range of the geographicarea, and that range may be based on the density of the area or theaccuracy of that estimated location (e.g., the accuracy of the locationdata).

Based on step 406 (e.g., method 500 and 600), a subset of devices 102may be identified, wherein each device 102 of the subset are estimatedto approach time segment within the time interval.

At step 408, additional filtering of devices 102 may be performed. Forexample, traffic event may be considered chronic. Thus, historicaltraffic patterns of devices 102 may be determined. If a particulardevice 102 frequently traverses the geographic area (and thus, regularlyencounters the traffic event), that device 102 may be filtered out ofthe subset. As another example, the traffic event may be based on datacollected from certain types of vehicles 103, while the acceleration orspeed patterns of other types of vehicles 103 may not be affected by thetraffic event. For example, a speed bump may be small enough that onlycompact cars slow down. Thus, first device 102 that is associated with afour-wheel drive SUV that is not surrounded by other compact cars, maybe filtered out of the subset.

At step 410, devices 102 of the subset, and other devices 102 that arepredicted to approach the geographic area within a time interval, may bealerted to the traffic event. This may include transmitting an alert todevice 102 within a certain amount of time (e.g., 1 minute) prior to theestimated time of arrival of that device 102 to the geographic area.Further, the alert may include specific details related to the trafficevent, including an indication of an absolute or relative location ofthe geographic area to device 102, a characteristic of the trafficevent, or an observed or estimated effect of the traffic event on thegeographic area, such as an approximate traffic speed at the geographicarea.

FIG. 4B is a flowchart of an exemplary method 412 for alerting devices102 of a traffic event. As compared to method 400, method 412 mayproduce a similar result—transmitting an alert indicative of the trafficevent to the subset of devices 102. One difference may be how method 412populates the subset of devices 102.

At step 414, method 400 may include receiving location data transmittedwithin a first time interval. Data transmitted within a first timeinterval may include, but not necessarily be limited to, data associatedwith a time existing within that first time interval or data timestampedwith a time contained in the first time interval. The location data maybe related to a plurality of devices 102. The first time interval may bepredefined, and it may be set at a threshold such that the location datawithin that time interval may be used to predict—with a desired degreeof accuracy—a current location or current trajectory of device 102. Thatis, location data may become “stale” or inaccurate for predicting howdevice 102 will move from that past location to future locations withina later second time interval. For example, using location data of device102 that indicates yesterday that device 102 was travelling north on aparticular highway to predict that the same device 102 has continued totravel in the direction on the same highway for the past twenty hoursmay have a low likelihood of being accurate. Whereas, in contrast,location data indicates device 102 was travelling in the same mannerfive minutes ago may be a more reliable predictor of that device 102continuing to travel in the same way five minutes later.

This manner of predicting trajectory may be different than, for example,detecting historical patterns based on past, repetitive behavior. Forexample, other location data transmitted outside of the first timeinterval may be used in this manner. For example, if location data ofdevice 102 within the first time interval indicates device 102 islocated near the workplace of the user of device 102, and the historicalbehavior of device 102 indicates that around 7:00 PM on weekdays device102 travels towards the home of the user of device 102, then suchlocation data, even though it is outside of the first time interval, maybe used to predict that device 102 will travel at a second timeinterval, around 7:00 PM, towards that home.

The type(s) and amount of location data for each device 102 may vary. Ata high level, location data may comprise data that indicates a locationor movement of device 102. For example, one or more devices 102, such asa first device 102, may be related to a plurality of GPS data pointsfrom within the first time interval. As another example, one or moredevices 102, such as a second device 102, may be related to a single GPSdata point from within the first time interval. As another example, oneor more devices 102, such as a third device 102, may indicate a velocityof third device 102. As yet another example, one or more devices 102 maybe related to no GPS data points from within that time interval.

To determine whether or not device 102 may be approaching a geographicarea within a second time interval, certain data may be more reliablethan others. For example, a location determined using GPS data pointsmay be more precise than a location determined using the cell id of thecell to which device 102 belongs. Further, while behavioral patterns maybe a good indicator, historical data may not account for certainanomalies, like if the user of device 102 is traveling from work to theairport instead of going home, as reliably as current GPS data mayindicate. Thus, identifying the subset of devices 102 that are likely toapproach the geographic area may use the most reliable data availablefor determining whether to include or exclude device 102 from the subsetof devices 102 receiving the alert.

The accuracy of the location data may depend upon the type of thelocation data. For example, GPS data points may have an accuracy on theorder of about 3.5 meters. As another example, device 102's detection ofaccess point 106 may indicate device 102's location with approximately400 meter accuracy. As another example, a cell id may identify ageographic location on the order of 1 to 30 kilometers. These accuraciesmay be affected based on specific factors in a given situation. Forexample, GPS data points may be less accurate in locations denselypopulated by high rises, as a result of multi-path interference. Asanother example, the accuracy of a location based on device 102detecting access point 106 may depend upon the operating characteristicsof access point 106. Further, the size of a cell (and in turn, theaccuracy of a location based on device 102 being in a cell) may varybased on density of base stations 104 in the area.

Location data may be compiled together to improve accuracy. For example,the accuracy of a location based on device 102 being able to sensemultiple access points 106 may be greater than if the location was basedonly on device 102 sensing a single access point 106. As anotherexample, further considering signal strengths along with those detectedaccess points 106 may further improve accuracy. Location data may alsoinclude analysis of raw location data. For example, location data mayinclude a Rayleigh fading rate, trilateration based on multiplelocations (and optionally signal strengths), or other known locationtechniques.

Step 414 may include identifying a subset of the plurality of devices102 that are within a vicinity of a geographic area affected by atraffic event. Populating the subset may comprise affirmativelyidentifying devices 102 that are within the vicinity, eliminating fromthe subset devices 102 that are outside of the vicinity, or anycombination thereof. For example, there may be devices 102 whoselocation data indicates that device 102 is far outside of the vicinity.For example, if the geographic area is located in Atlanta, Ga., and aparticular device 102 is located—based on its location data—in Dayton,Ohio, that distant device 102 may be filtered from the subset. Asanother example, if the geographic area is located on 14th Street inAtlanta, and the location data indicates that another device 102 istraveling down that street, that device 102 may be included in thesubset. There may be other devices, 102 for example, that have locationdata that does not clearly indicate whether device 102 is inside oroutside of the subset. For example, if the location data indicates thatanother device 102 is within a cell that encompasses—but is not entirelymade of—the vicinity, then depending upon the specific implementation orother factors that device may or may not be included in the subset.

Identifying devices 102 within a vicinity of the geographic area may bebased on the accuracy of location data associated with that particulardevice 102. For example, if the location of device 102 is based on GPSdata points, the vicinity may be a first threshold. As another example,if the location of another device 102 is based on lower-accuracy data,such as cell id, then the vicinity may differ. For example, it may bedesirable to filter out those devices 102 that, based on their GPSlocation, are more than 1 km downstream of the geographic area (e.g.,such that their GPS location indicates that even if such device 102 istraveling in the direction of the geographic area, the device 102 hasalready passed the traffic event). On the other hand, it may not beappropriate to eliminate devices 102 whose only location data indicatesthat they are within the cell that includes that location 1 kmdownstream of the geographic area, particularly if the same cell alsoincludes the geographic area and another geographic area that iscontiguous to and upstream of the geographic area affected by thetraffic event.

The subset of devices 102 may be filtered further. The specific ways inwhich devices 102 are filtered (or not) may vary depending upon thecontents of the location data transmitted within the first time intervalthat is related to that particular device.

For example, location data of certain devices 102 of the subset mayindicate that those certain devices are not moving, or that theirvelocity does not meet a minimum threshold. These devices may befiltered out of the subset. For example, returning to the exemplarythird device 102 whose location data indicates the velocity of the thirddevice 102, that velocity may low enough to indicate that third device102 will not be affected by the traffic event. This includes devices 102whose velocity indicates the devices 102 are actually not moving, suchas a mobile device 102 that is sitting unused on a table. This may alsoinclude devices 102 whose location information indicates that theirvertical velocity is much greater than their latitudinal or longitudinalvelocity, which may suggest that device 102 is in an elevator orstairwell. It may also indicate devices 102 whose velocity suggestsdevices 102 are being used by pedestrians, or people inside ofbuildings. The velocity threshold may vary. For example, the velocitythreshold may be a function of the traffic flow of that area. Forexample, velocities indicating movement at 2 miles per hour may, undersome circumstances, indicate a pedestrian-used device 102, but iftraffic is congested, that device 102 may be sitting in a vehicle instop-and-go traffic. Thus, the velocity threshold may be tailoreddepending upon certain factors.

At steps 420 and 422, additional devices 102 may be filtered out of thesubset based on their location data indicating that those devices 102will not approach the geographic area within a second time interval. Atstep 420, it may be determined that certain devices 102 will notapproach the geographic area within the second time interval based ontheir respective location data. The specific location data of eachdevice 102 that may be considered in making this determination may vary.For example, for a first device 102 whose location data transmittedwithin the first time interval includes multiple GPS data points, thisdetermination may be based on at least those GPS data points. But forother devices, such as the second device 102 whose location datatransmitted within the first time interval may not contain more than asingle GPS data point, other information, such as a second locationdatum, may be relied upon. For example, the second location datum maycomprise non-GPS information transmitted within (or outside of) thefirst time interval. For example, the second location datum may comprisea cell identifier, a Wi-Fi location, access point 106 detected by seconddevice 102, an access point handoff, or a Rayleigh fading rate. Asanother example, the second location datum may comprise a second GPSdata point of second device 102 that was transmitted or timestampedoutside of the first time interval. For example, such GPS data pointsmay be used to predict historical behaviors of second device 102, asdiscussed above. Such determinations that device 102 will not approachthe geographic area may be performed similarly to those determinationsthat device 102 will approach the geographic area, such as those methodsdiscussed in FIGS. 5 and 6.

Other methods for determining whether device 102 may approach thegeographic location within the second time interval may be used, and theselection of which method to use may depend upon the location dataavailable for that device. For example, as discussed above, locationdata transmitted within the first time interval may include no GPS datapoints. Determination of whether to filter out or to include suchdevices 102 may depend upon determining whether such device 102 ismoving, such as indicated by second location data of that device, theaccuracy of such determinations, and the density of the geographic area,as discussed above. For example, the higher the density of thegeographic area, the lower the accuracy of such location data may berequired to include or exclude the related device 102 in or from thesubset.

Once devices 102 determined to not approach the geographic area arefiltered out of the subgroup at step 422, at step 424, an alert may besent to the subset.

FIG. 7 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 700 related to the current disclosure.In particular, the network architecture 700 disclosed herein is referredto as a modified LTE-EPS architecture 700 to distinguish it from atraditional LTE-EPS architecture.

An example modified LTE-EPS architecture 700 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. In one embodiment, theLTE-EPS network architecture 700 includes an access network 702, a corenetwork 704, e.g., an EPC or Common BackBone (CBB) and one or moreexternal networks 706, sometimes referred to as PDN or peer entities.Different external networks 706 can be distinguished from each other bya respective network identifier, e.g., a label according to DNS namingconventions describing an access point to the PDN. Such labels can bereferred to as Access Point Names (APN). External networks 706 caninclude one or more trusted and non-trusted external networks such as aninternet protocol (IP) network 708, an IP multimedia subsystem (IMS)network 710, and other networks 712, such as a service network, acorporate network, or the like. Network 110 or network 114 may includeone or more access networks 702, core networks 704, or an externalnetworks 706.

Access network 702 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 702 can include one ormore communication devices, commonly referred to as UE 714, and one ormore wireless access nodes, or base stations 716 a, 716 b. Duringnetwork operations, at least one base station 716 communicates directlywith UE 714. Base station 716 can be an evolved Node B (e-NodeB), withwhich UE 714 communicates over the air and wirelessly. UEs 714 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 714 can connect to eNBs716 when UE 714 is within range according to a corresponding wirelesscommunication technology.

UE 714 generally runs one or more applications that engage in a transferof packets between UE 714 and one or more external networks 706. Suchpacket transfers can include one of downlink packet transfers fromexternal network 706 to UE 714, uplink packet transfers from UE 714 toexternal network 706 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 704, e.g., according to parameters, such as the QoS.

Core network 704 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network704 and UE 714. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 714. Access network702, e.g., E UTRAN, and core network 704 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

Core network 704 may include various network entities, such as MME 718,SGW 720, Home Subscriber Server (HSS) 722, Policy and Charging RulesFunction (PCRF) 724 and PGW 726. For example, MME 718 may include acontrol node performing a control signaling between various equipmentand devices in access network 702 and core network 704. The protocolsrunning between UE 714 and core network 704 are generally known asNon-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 718, SGW 720, HSS 722 andPGW 726, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW720 routes and forwards all user data packets. SGW 720 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 716 a to second eNB 716b as may be the result of UE 714 moving from one area of coverage, e.g.,cell, to another. SGW 720 can also terminate a downlink data path, e.g.,from external network 706 to UE 714 in an idle state, and trigger apaging operation when downlink data arrives for UE 714. SGW 720 can alsobe configured to manage and store a context for UE 714, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 720 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), or replicate user traffic, e.g., to support a lawfulinterception. SGW 720 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 714 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 714 is powered on but is engaged in a process ofsearching and registering with network 702. In the active state, UE 714is registered with access network 702 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 716.Whether UE 714 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 714 is generally in a power conservation state in whichUE 714 typically does not communicate packets. When UE 714 is idle, SGW720 can terminate a downlink data path, e.g., from a peer entity such asnetwork 706, and triggers paging of UE 714 when data arrives for UE 714.If UE 714 responds to the page, SGW 720 can forward the IP packet to eNB716 a.

HSS 722 can manage subscription-related information for a user of UE714. For example, tHSS 722 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 722 can also hold informationabout external networks 706 to which the user can connect, e.g., in theform of an APN of external networks 706. For example, MME 718 cancommunicate with HSS 722 to determine if UE 714 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 724 can perform QoS management functions and policy control. PCRF724 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 726. PCRF 724 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 726 can provide connectivity between the UE 714 and one or more ofthe external networks 706. In illustrative network architecture 700, PGW726 can be responsible for IP address allocation for UE 714, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 724. PGW 726 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 726 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 726 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 702 and core network 704 there may be variousbearer paths/interfaces, e.g., represented by solid lines 728 and 730.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 728 can be considered an S1-U bearer and solid line732 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 704 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 730, 734, 736, and 738. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 730 can be considered as an S1-MME signalingbearer, dashed line 734 can be considered as an S11 signaling bearer anddashed line 736 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 766. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 716 a and PGW 726. Notably, S1-U+path/interface does not include SGW 720, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 716 a and one or more external networks 706 by way of PGW 726. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs720, 726 due to excessive handover events.

In some embodiments, PGW 726 is coupled to storage device 740, shown inphantom. Storage device 740 can be integral to one of the network nodes,such as PGW 726, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 740 can include registerssuitable for storing address values. Alternatively or in addition,storage device 740 can be separate from PGW 726, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 740 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 740 can storeidentities and/or addresses of network entities, such as any of networknodes 718, 720, 722, 724, and 726, eNBs 716 and/or UE 714. In theillustrative example, storage device 740 includes a first storagelocation 742 and a second storage location 744. First storage location442 can be dedicated to storing a Currently Used Downlink address value742. Likewise, second storage location 744 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 726 can read and/orwrite values into either of storage locations 742, 744, for example,managing Currently Used Downlink Forwarding address value 742 andDefault Downlink Forwarding address value 744 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 726 can beset every time when PGW 726 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 714 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 714 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 726 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 726 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 720.

As values 742, 744 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 702 and core network 704 areillustrated in a simplified block diagram in FIG. 7. In other words,either or both of access network 702 and the core network 704 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 7illustrates only a single one of each of the various network elements,it should be noted that access network 702 and core network 704 caninclude any number of the various network elements. For example, corenetwork 704 can include a pool (i.e., more than one) of MMEs 718, SGWs720 or PGWs 726.

In the illustrative example, data traversing a network path between UE714, eNB 716 a, SGW 720, PGW 726 and external network 706 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 700, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 700. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 746) between UE 714 and eNB 716 a, a secondportion (e.g., an S1 data bearer 728) between eNB 716 a and SGW 720, anda third portion (e.g., an S5/S8 bearer 732) between SGW 720 and PGW 726.Various signaling bearer portions are also illustrated in FIG. 7. Forexample, a first signaling portion (e.g., a signaling radio bearer 748)between UE 714 and eNB 716 a, and a second signaling portion (e.g., S1signaling bearer 730) between eNB 716 a and MME 718.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of networkarchitecture 700, e.g., by one or more of tunnel endpoint identifiers,an IP address and a user datagram protocol port number. Within aparticular tunnel connection, payloads, e.g., packet data, which may ormay not include protocol related information, are forwarded betweentunnel endpoints.

An example of first tunnel solution 750 includes a first tunnel 752 abetween two tunnel endpoints 754 a and 756 a, and a second tunnel 752 bbetween two tunnel endpoints 754 b and 756 b. In the illustrativeexample, first tunnel 752 a is established between eNB 716 a and SGW720. Accordingly, first tunnel 752 a includes a first tunnel endpoint754 a corresponding to an S1-U address of eNB 716 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 756 a correspondingto an S1-U address of SGW 720 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 752 b includes first tunnel endpoint754 b corresponding to an S5-U address of SGW 720 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 756 b corresponding toan S5-U address of PGW 726 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 750 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPvl-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 758 includes a single or directtunnel 760 between tunnel endpoints 762 and 764. In the illustrativeexample, direct tunnel 760 is established between eNB 716 a and PGW 726,without subjecting packet transfers to processing related to SGW 720.Accordingly, direct tunnel 760 includes first tunnel endpoint 762corresponding to the eNB S1-U address, and second tunnel endpoint 764corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 720 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 758 can forward user planedata packets between eNB 716 a and PGW 726, by way of SGW 720. That is,SGW 720 can serve a relay function, by relaying packets between twotunnel endpoints 716 a, 726. In other scenarios, direct tunnelingsolution 758 can forward user data packets between eNB 716 a and PGW726, by way of the S1 U+ interface, thereby bypassing SGW 720.

Generally, UE 714 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 750, 758, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 714, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 714 can have another bearer associatedwith it through the same eNB 716 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 704 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 758; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 750.

FIG. 8 is an example system 800 including RAN 108 and core network 110.As noted above, RAN 108 may employ an E-UTRA radio technology tocommunicate with devices 102 over air interface. RAN 108 may also be incommunication with core network 110.

RAN 108 may include any number of eNode-Bs 716 while remainingconsistent with the disclosed technology. One or more eNode-Bs 716 mayinclude one or more transceivers for communicating with the devices 102over air interface. Optionally, eNode-Bs 716 may implement MIMOtechnology. Thus, one of eNode-Bs 716, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of Devices 102.

Each of eNode-Bs 716 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 716 may communicatewith one another over an X2 interface.

Core network 110 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 718, a serving gateway 720, or a packet datanetwork (PDN) gateway 726. While each of the foregoing elements aredepicted as part of core network 110, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 718 may be connected to each of eNode-Bs 716 in RAN 108 via an S1interface and may serve as a control node. For example, MME 718 may beresponsible for authenticating users of devices 102, bearer activationor deactivation, selecting a particular serving gateway during aninitial attach of devices 102, or the like. MME 718 may also provide acontrol plane function for switching between RAN 108 and other RANs (notshown) that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 716 in RAN 108via the S1 interface. Serving gateway 720 may generally route or forwarduser data packets to or from the devices 102. Serving gateway 720 mayalso perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for devices 102, managing or storing contexts of devices 102,or the like.

Serving gateway 720 may also be connected to PDN gateway 726, which mayprovide devices 102 with access to packet-switched networks, such asInternet 112, to facilitate communications between devices 102 andIP-enabled devices.

Core network 110 may facilitate communications with other networks. Forexample, core network 110 may provide devices 102 with access tocircuit-switched networks, such as PSTN 113, to facilitatecommunications between devices 102 and traditional land-linecommunications devices. In addition, core network 110 may provide thedevices 102 with access to other networks 114, which may include otherwired or wireless networks that are owned or operated by other serviceproviders.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., device102, network device 300, or the like, or any combination thereof). Radioaccess network 904 comprises a plurality of BSSs such as BSS 912, whichincludes a BTS 914 and a BSC 916. Core network 906 may include a host ofvarious network elements. As illustrated in FIG. 9, core network 906 maycomprise MSC 918, service control point (SCP) 920, gateway MSC (GMSC)922, SGSN 924, home location register (HLR) 926, authentication center(AuC) 928, domain name system (DNS) server 930, and GGSN 932.Interconnect network 908 may also comprise a host of various networks orother network elements. As illustrated in FIG. 9, interconnect network908 comprises a PSTN 934, an FES/Internet 936, a firewall 1038, or acorporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 10, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, device 102, vehicle 103, network device 300,the like, or any combination thereof may serve as MS 1002. MS 1002 maybe one of, but not limited to, a cellular telephone, a cellulartelephone in combination with another electronic device or any otherwireless mobile communication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location data such as, butnot limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation data.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location data. HSS 1042 may also provide call or sessionestablishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location data to the VLR for thearea. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

While examples of a telecommunications system in which vehicle alertscan be generated and communicated have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

What is claimed:
 1. A method comprising: receiving, at a network deviceof a network, location data transmitted during a first time interval,the location data being related to a plurality of devices, wherein thelocation data includes at least two global positioning system (GPS) datapoints of a first device, a single GPS data point of a second device,and information related to a velocity of a third device; identifying,based at least on the location data, a subset of the plurality ofdevices that are within a vicinity of a geographic area associated witha traffic event, the subset comprising the first device, the seconddevice, the third device, and a fourth device; filtering, by the networkdevice, the third device from the subset based at least on theinformation related to the velocity of the third device indicating thatthe velocity of the third device does not exceed a threshold;determining that the first device will not approach the geographic areaduring a second time interval based at least on the at least two GPSdata points; determining that the second device will not approach thegeographic area during the second time interval based at least on thesingle GPS data point and a second location datum; filtering, by thenetwork device, the first device and the second device from the subset;and transmitting, via the network, an alert indicative of the trafficevent to the subset.
 2. The method of claim 1, wherein each datum of thelocation data is associated with at least one time within the first timeinterval.
 3. The method of claim 1, wherein the second location datumcomprises a second GPS data point of the second device, the second GPSdata point transmitted prior to the first time interval.
 4. The methodof claim 1, wherein the at least two GPS data points are timestampedwithin the first time interval.
 5. The method of claim 1, wherein thesingle GPS data point is timestamped within the first time interval. 6.The method of claim 1, wherein the location data of the second devicecomprises the second location datum, and wherein a type of the secondlocation datum is non-GPS data.
 7. The method of claim 1, wherein thesecond location datum comprises a cell identifier, a Wi-Fi location, anaccess point detected by the second device, an access point handoff, ora Rayleigh fading rate.
 8. The method of claim 1, wherein the subsetfurther comprises a fifth device, the method further comprising:comparing the traffic event to a historical traffic pattern for thegeographic area; based on the comparing, determining that the trafficevent is chronic; and prior to transmitting the alert, filtering thesubset to exclude the fourth device based on the fourth device havingpreviously traversed the geographic area.
 9. The method of claim 1,further comprising: receiving, via the network, sensor data from aplurality of sources; deriving, based on the sensor data, anacceleration pattern for the geographic area; and identifying thetraffic event based at least on the acceleration pattern.
 10. A systemcomprising: an input/output; a processor communicatively coupled to theinput/output; and memory storing instructions that cause the processorto effectuate operations, the operations comprising: receiving, via theinput/output, location data transmitted during a first time interval,the location data being related to a plurality of devices, wherein thelocation data includes at least two global positioning system (GPS) datapoints of a first device, a single GPS data point of a second device,and information related to a velocity of a third device; identifying,based at least on the location data, a subset of the plurality ofdevices that are within a vicinity of a geographic area associated witha traffic event, the subset comprising the first device, the seconddevice, the third device, and a fourth device; filtering the thirddevice from the subset based at least on the information related to thevelocity of the third device indicating that the velocity of the thirddevice does not exceed a threshold; determining that the first devicewill not approach the geographic area during a second time intervalbased at least on the at least two GPS data points; determining that thesecond device will not approach the geographic area during the secondtime interval based at least on the single GPS data point and a secondlocation datum; filtering the first device and the second device fromthe subset; and transmitting, via the input/output, an alert indicativeof the traffic event to the subset.
 11. The system of claim 10, whereinthe at least two GPS points of the first device comprise GPS datagenerated by a related device related to the first device.
 12. Thesystem of claim 10, wherein the single GPS data point of the seconddevice comprises GPS data generated by a related device related to thesecond device.
 13. The system of claim 10, wherein the location datarelated to the second device comprises the second location datum, andwherein a type of the second location datum is non-GPS data.
 14. Thesystem of claim 10, wherein the second location datum comprises a secondGPS data point of the second device, wherein a timestamp of the secondGPS data point of the second device is outside of the first timeinterval.
 15. A method comprising: receiving, at a network device of anetwork, location data transmitted during a first time interval, thelocation data being related to a plurality of devices, wherein thelocation data includes at least two global positioning system (GPS) datapoints of a first device and a single GPS data point of a second device;identifying, based at least on the location data, a subset of theplurality of devices by filtering out a distant device that is outsideof a vicinity of a geographic area associated with a traffic event, thesubset comprising the first device, the second device, and a thirddevice; determining that the first device will not approach thegeographic area during a second time interval based at least on the atleast two GPS data points; determining that the second device will notapproach the geographic area during the second time interval based atleast on the single GPS data point and a second location datum;filtering, by the network device, the first device and the second devicefrom the subset; and transmitting, via the network, an alert indicativeof the traffic event to the subset.
 16. The method of claim 15, whereinthe second location datum comprises a cell identifier, a Wi-Fi location,an access point detected by the second device, an access point handoff,or a Rayleigh fading rate.
 17. The method of claim 15, wherein thesubset comprises a fourth device, and the location data of the thirddevice comprises no GPS data points, the method further comprising:estimating a movement of the third device based on the location data ofthe third device, the movement indicating that the third device ismoving towards the geographic area; determining a density of thegeographic area; and filtering the third device from the subset based onthe density.
 18. The method of claim 17, further comprising: determiningan accuracy of the estimated movement, wherein filtering the thirddevice from the subset is further based on the accuracy.
 19. The methodof claim 15, wherein the location data related to the first devicecomprises location data of a related device associated with the firstdevice.
 20. The method of claim 15, wherein the location data related tothe second device comprises location data of a related device associatedwith the second device.